fix(ci): publish resilience + deps:tree fix + GitNexus license correction#36
Merged
carlos-alm merged 4 commits intomainfrom Feb 23, 2026
Merged
fix(ci): publish resilience + deps:tree fix + GitNexus license correction#36carlos-alm merged 4 commits intomainfrom
carlos-alm merged 4 commits intomainfrom
Conversation
GitNexus uses PolyForm Noncommercial License 1.0.0, not MIT. Add "Commercial use allowed" row to README feature comparison table.
The inline node -e command had backticks that sh on Linux interpreted as command substitution, causing `sh: 1: n+t+: not found`. Also, npm ls exits non-zero on ELSPROBLEMS (version mismatches in optional platform-specific deps), which made execSync throw during publish. Fix: move to scripts/gen-deps.cjs with try/catch to handle npm ls failures gracefully, and use --omit=dev to exclude devDependencies.
Add version-exists checks so re-running a failed publish skips already-published packages instead of failing with 409 Conflict. - Check main package before publish steps; if already on npm, skip both platform and main publish (post-publish steps still run) - Check each platform package individually before npm publish; skip with continue if already published
Contributor
Greptile SummaryCombines 4 bug fixes and 1 documentation correction:
The workflow changes enable safe retries of failed stable releases via Confidence Score: 4/5
Important Files Changed
Last reviewed commit: 73a1e6b |
Comment on lines
+238
to
+242
| # Skip if this exact version is already published (idempotent re-runs) | ||
| if npm view "${pkg_name}@${VERSION}" version 2>/dev/null; then | ||
| echo "⚠️ ${pkg_name}@${VERSION} already published — skipping" | ||
| continue | ||
| fi |
Contributor
There was a problem hiding this comment.
verify that all 4 platforms in PACKAGES map exactly to the 4 matrix builds in the build-native job. if the matrix changes but PACKAGES doesn't update, publishes could be incomplete.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Combines all pending unmerged work from stale branches into one PR.
scripts/gen-deps.cjs— the inlinenode -ehad backticks thatshon Linux interpreted as command substitution (sh: 1: n+t+: not found), andnpm lsnon-zero exit on ELSPROBLEMS threw inexecSync. New script handles both with try/catch.npm viewchecks before each platform package publish (skip if already on npm), and gate both publish steps on acheck-mainoutput so re-running a partially failed publish doesn't 409.Branches superseded by this PR
fix/publish-resilience(fix(ci): fix deps:tree publish failure and add publish resilience #35)fix/deps-omit-devfix/publish-workflow-dispatchdocs/add-gitnexus-competitorfeat/multi-repo-mcp(tagline change skipped — HEAD content is better)Test plan
@optave/codegraphpublishes successfullynpm run deps:treeworks on Linux CI without backtick errors